Automated digital voice recorder to personal information manager synchronization

ABSTRACT

Apparatus and methods are presented for Automated Digital voice recorder to Personal information manager Synchronization (ADPS) message creation that allow a user to indicate that an ADPS message is to be created, select and ADPS type selection relating the ADPS message to be created to a type of Personal Information. Manager (PIM) application, record audio content for the ADPS message, and create an ADPS message by organizing the ADPS type selection and the audio content into the ADPS message and store the ADPS message in the memory. Apparatus and methods are presented for downloading ADPS messages directly to a target PIM application. Apparatus and methods are presented for uploading configuration modifications and informational lists to the DVR. This abstract is not to be considered limiting, since other embodiments may deviate from the features described in this abstract without departing from certain embodiments of the invention.

CROSS REFERENCE TO RELATED DOCUMENTS

This application is a continuation of pending U.S. application Ser. No.10/632,029 filed Jul. 31, 2003 now U.S. Pat. No. 7,149,693, which ishereby incorporated by reference.

TECHNICAL FIELD

This invention relates generally to the field of digital voicerecording. Certain embodiments consistent with this invention relate toautomated conversion and transfer of voice messages between digitalvoice recorders (DVRs) and integrated circuit (IC) recorders of audiosignals, and personal information manager (PIM) software applications ona personal computer (PC).

BACKGROUND

In the last few decades electronic voice recorders have been used tocapture thoughts and messages, summarize ideas, and document eventsacross a variety of business and personal applications. Storage andplayback of audio recordings has traditionally taken place on analogmedia or devices. More recently, the use of digital media and deviceshas become possible. In recent years the use of magneto-optical, solidstate and Micro Drive digital storage technologies has triggered growthin use of digital audio self-recorded content. Accordingly, the numberof Digital Voice Recorders (DVRs) has been growing in the last fewyears. DVRs have provided various benefits over analog voice recorders.

DVRs incorporate file-based content transfer capability. This capabilityhas been performed, for example, by USB connectivity or by compatibilitywith a digital file removable storage media such as Memory Stick™available also on the PC, along with many other transfer mechanismsknown to those skilled in the art. In recent years, digital voicerecording capabilities have been expanded from dedicated voice recordersto other consumer electronic categories. These categories have includeddigital music players with MP3 or ATRAC3 file playback capabilities,Cellular phones or Personal Digital Assistants (PDA) devices with builtin or external microphone input, and digital imaging devices capable ofimage, text, or video as well as audio recording. All of these and otherdevices may be considered DVR devices for purpose of this document aslong as they can be adapted to download audio files recorded on thedevice to a computer (PC), or upload content created on a PC to a DVR.

In recent years the PC has taken an important role as an entertainmentdevice in a large number of households, as well as a business tool inthe home and office. The PC has been used not only as a data depositoryand processing center for information such as documents, spreadsheetsand audiovisual content, but also as a center for communications,scheduling and lifestyle management. Handling contact, calendar, andtask information on the PC has often been done via software packagesknown as Personal Information Manager (PIM) applications. PIM softwarepackages have assisted in facilitating email communications, timemanagement, and responsibility tracking, to name a few. In many casesthese PIM applications have also served as a vehicle of communicationbetween a professional, such as a medical doctor, attorney, or abusiness manager, and their administrator. This communication vehiclehas been provided via sharing access rights to schedule, tasks, andemail between two computers located in the same office or two computingdevices using a computer network such as a local area network or theInternet.

OVERVIEW OF CERTAIN EMBODIMENTS

The present invention relates generally to digital voice recording.Objects, advantages and features of certain embodiments of the inventionwill become apparent to those skilled in the art upon consideration ofthe following detailed description of the invention.

In one embodiment consistent with the present invention an apparatus forAutomated Digital voice recorder to Personal information managerSynchronization (ADPS) has an interface that receives at least one voicefile containing audio content and related information from a digitalvoice recorder (DVR) and a memory. A processor is programmed to carryout reading information in the voice file that associates audio contentwithin the voice file with a personal information manager (PIM)application and processing the voice file by transferring the voice fileto at least one PIM application.

In another embodiment consistent with the present invention an apparatusfor Automated Digital voice recorder to Personal information managerSynchronization (ADPS) has an interface that enables file transfer to aDigital Voice Recorder (DVR). A processor is programmed that transfersat least one voice file containing audio content and related informationfrom a Personal Information Manager (PIM) application across theinterface to the DVR.

In another embodiment consistent with the present invention an apparatusfor Automated Digital voice recorder to Personal information managerSynchronization (ADPS) message creation has a microphone and an analogto digital converter that converts analog microphone input signals toaudio content in a digital format, a memory, and a user interface. Aprocessor is programmed to receive an indication that an ADPS message isto be created, an ADPS type selection relating the ADPS message to becreated to a type of Personal Information Manager (PIM) application, astart signal to begin recording audio content for the ADPS message to becreated, and a stop signal to stop recording the audio content for theADPS message to be created from the user interface. The processor thencreates an ADPS message by organizing the ADPS type selection and theaudio content into the ADPS message and storing the ADPS message in thememory.

The above overviews are intended to illustrate exemplary embodiments ofthe invention, which will be best understood in conjunction with thedetailed description to follow, and are not intended to define or limitthe scope of the appended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The features of the invention believed to be novel are set forth withparticularity in the appended claims. The invention itself however, bothas to organization and method of operation, together with objects andadvantages thereof, may be best understood by reference to the followingdetailed description, which describes certain exemplary embodiments ofthe invention, taken in conjunction with the accompanying drawings inwhich:

FIG. 1 is an Automatic DVR-to-PIM Download System (ADPS) consistent withcertain embodiments of the present invention.

FIG. 2 is an ADPS message creation flow diagram consistent with certainembodiments of the present invention.

FIG. 3 is an internal DVR ADPS message creation flow diagram consistentwith certain embodiments of the present invention.

FIG. 4 is an ADPS message consistent with certain embodiments of thepresent invention.

FIG. 5 is an ADPS message header consistent with certain embodiments ofthe present invention.

FIG. 6 is an ADPS download process consistent with certain embodimentsof the present invention.

FIG. 7 is an ADPS download system block diagram consistent with certainembodiments of the present invention.

FIG. 8 is another ADPS system consistent with certain embodiments of thepresent invention.

FIG. 9 is another internal DVR ADPS message creation flow diagramconsistent with certain embodiments of the present invention.

FIG. 10 is an ADPS Upload process consistent with certain embodiments ofthe present invention.

FIG. 11 is a block diagram of a DVR consistent with certain embodimentsof the present invention.

FIG. 12 is a block diagram of a computer consistent with certainembodiments of the present invention.

DETAILED DESCRIPTION

While this invention is susceptible of embodiment in many differentforms, there is shown in the drawings and will herein be described indetail specific embodiments, with the understanding that the presentdisclosure is to be considered as an example of the principles of theinvention and not intended to limit the invention to the specificembodiments shown and described. In the description below, likereference numerals are used to describe the same, similar, orcorresponding parts in the several views of the drawings.

The terms “a” or “an”, as used herein, are defined as one or more thanone. The term “plurality”, as used herein, is defined as two or morethan two. The term “another”, as used herein, is defined as at least asecond or more. The terms “including” and/or “having”, as used herein,are defined as comprising (i.e., open language). The term “coupled”, asused herein, is defined as connected, although not necessarily directly,and not necessarily mechanically. The term “program”, as used herein, isdefined as a sequence of instructions designed for execution on acomputer system. A “program”, or “computer program”, may include asubroutine, a function, a procedure, an object method, an objectimplementation, in an executable application, an applet, a servlet, asource code, an object code, a shared library/dynamic load libraryand/or other sequence of instructions designed for execution on acomputer system.

Audio information related to email communications, time management,scheduling, address management, or responsibility tracking can becaptured on a DVR and transferred to a PC using the manual downloadcapability provided by some DVRs. A DVR capable of downloading an audiofile to the PC is often compatible with a software package that wasdesigned specifically for it. In these cases, an audio file created onthe DVR is transferred to this DVR Dedicated Software Application (DSA)on the PC via a manual file transfer over a USB interface, or othertransfer mechanism known to those skilled in the art. Once the audiofile is downloaded to the PC, the DSA may be used to manipulate the file(listening, managing, sharing, etc.).

Unfortunately, the existing DVR-to-PC synchronization experience iscumbersome, time consuming, and requires technical understanding of filemanagement and software. The process involves manual user interactionwith either the DSA or another application on the PC. These tasks may bea challenge depending on file naming convention, number of files alreadyin the DSA, and simplicity of that application's user interface. Oftenthis manual interaction involves listening to individual files and theircontent in order to remember what was recorded and for what purpose.

In many cases the user knows the intention in creating the audiomessage, or alternatively, the nature of the recording, before therecording takes place. However, without capturing their intention inrecording that message at time of creation, they may be forced toreestablish their thoughts later on during file search on the PC.Further, a download of audio information recorded on a device directlyto a PIM function, or conversely, an upload of information from a PIMfunction to a DVR, may be desired.

A mechanism, consistent with certain embodiments of the invention, toenable capture of the PIM destination (the target PIM application) forthe recording, automatic download and processing of a message from theDVR directly to the appropriate PIM function, and automatic upload andprocessing of a message created in a PIM to a DVR is referred to in thisdocument as the Automatic DVR-to-PIM Synchronization system (ADPS). AnADPS type message is a combination of an audio recording (or messagecontent) and the information to allow processing of the message in theADPS system. One exemplary ADPS enabled or activated device is a DVRthat is capable of recording an ADPS type message and transferring it toa computer or other device, or a computer or other device that iscapable of processing the ADPS message. This mechanism can genericallybe discussed as Automated Voice File Processing (AVFP).

As noted above, PIM applications include email, calendar and scheduling,task lists (To Do List), time management, address management,responsibility tracking, and many other applications designed to enhancea PC, or comparable product, user's productivity and simplify theiractivities.

Turning now to FIG. 1, one embodiment of an ADPS system 100 is shown.DVR 104 is connected through an appropriate mechanism, such as a USBconnection 108 in this embodiment or by physical transfer of a removablemedia such as a memory stick, to a PC or comparable device 112, toenable download of an ADPS message 116 from an ADPS database 120 withinDVR 104 to the PC 112. It should be noted, and should now be evident tothose skilled in the art in view of this disclosure, that many otherconnection mechanisms (eg. Ethernet, infrared, wireless, serial,parallel, IEEE 1394, or any other suitable communication interface) canbe used to connect the DVR 104 to the PC 112. Connection mechanisms,such as any standard or custom wireless protocol, or any other effectivecommunication mechanism can be used for interconnection of DVR 104 to PC112. When the DVR 104 is connected to PC 112, the ADPS message 116 isautomatically downloaded to the appropriate target PIM applicationwithout a need to launch the DSA. In certain embodiments, there is nosoftware launch required at all as will be discussed below.

Turning now to FIG. 2, an exemplary user ADPS message creation flowdiagram 200 is shown. This diagram starts at 204. At 208, the userdetermines whether to create an ADPS message 116 or a standard audiorecording. If the user wants to create a standard audio recording, theuser presses the record button at 212, and then at 216, the user pressesthe stop button to terminate the recording and the process ends at 220.

However, if the user wants to create an ADPS message 116 at 208, then at224, the user uses a control mechanism on the DVR 104, such as pressinga MENU key, to initiate an ADPS message 116. At 228, the user uses acontrol mechanism, such as pressing a DOWN button, on the DVR 104 toselect the ADPS message type (determines which PIM application is thetarget) to create from a list that is available on the DVR 104. At 232,the user uses a control mechanism on the DVR 104, such as manual entryof data in this embodiment, to provide any information related to theADPS message 116 later on PC 112. Relevant information for the differentADPS messages defined in this embodiment will be discussed below. Afterthe user has fully or adequately specified the information, if any, forthe ADPS message 116, the user then presses the record button at 212 torecord the voice information. At 216, the user presses the stop buttonto terminate the recording and the process ends at 220.

It should be noted that many other control mechanisms for identifyingthat the user wishes to create an ADPS message are possible. Voicequeues and commands could be used through a voice recognition mechanismon the DVR 104 to initiate an ADPS message recording, to select the ADPSmessage type, and to enter any relevant information for the ADPSmessage, as well as for starting and stopping the recording process.Further, a touch screen and user interface, independent of or along withthe vocal queues discussed above, is another possible solution. Thoseskilled in the art should now be able to recognize a variety ofpossibilities for ADPS message indication, ADPS type, and ADPSinformation entry and control of the apparatus in view of the presentdisclosure.

As well, with regard to information related to ADPS messages, theinformation can also be entered by recording an audio note. That audionote can be later transcribed on the PC 112 or can be transcribed on theDVR 104 itself if speech to text technology is incorporated into the DVR104 firmware.

Turning now to FIG. 3, an internal DVR ADPS message creation flowdiagram 300 is shown. The flow starts at 304. At 308, an indication thatan ADPS message is to be created is received from the user by any one ofthe previously mentioned or other possible control mechanisms. At 312,the ADPS message type selection and the computer target is received fromthe user. As mentioned above, in this embodiment the ADPS message typeis selected from a list of possible ADPS message types that the user canchoose from, and is also chosen by any one of the previously mentionedor other possible mechanisms. In the present embodiment, three differentADPS message types will be considered for simplicity, but these threeADPS message types should not be considered an exhaustive list ofpossible message types. The ADPS message types in this embodiment are anemail message, a schedule event, and a task for a to-do list, but thisshould not be considered limiting. It should be noted that many otherADPS message types are possible and are considered consistent with thisdisclosure. The computer target selected at this stage could be anindication of “business” or “personal” in a simplified embodiment. Thesimplified selection of business or personal can, for example, allow auser to indicate to a secretary that the secretary should download allbusiness related emails for processing while leaving the personalmessages undisturbed on DVR 104. The computer target selection can, forexample, also be a selection from a list of computers (eg. PCx, PCy,Laptop1, PC1, PC2) uploaded to DVR 104 with a process discussed below.This uploaded list option allows the user to select the specificcomputer that is a part of their network as the target computer. Otheroptions for the computer target will be apparent to those skilled in theart based upon this disclosure.

At 316, the ADPS message type selection is evaluated to determinewhether an email message type was chosen. If so, an indication iscommunicated to the user that the DVR 104 is ready to record an emailmessage at 320. This indication can be communicated by use of visualdisplay, such as a Liquid Crystal Display (LCD) message, an audible beepor other indication, a previously recorded or digitally created verbalindication, or any of a variety of other possible methods. At 324, anindication to start recording by any one of the possible methodsdiscussed above is received and the recording process begins at 326. At328, an indication to stop the recording by any one of the possiblemethods discussed above is received and the recording process stops. Theinternal DVR ADPS message creation flow 300 stops at 332.

If the ADPS message type selected by the user is not an email message at316, the selection is evaluated at 336 to determine whether a scheduleevent was chosen. If so, other related information, for example, thedate and time of the scheduled event is received at 340, by any one ofthe possible methods discussed above, and this information is storedalong with the ADPS message type as will be discussed later.

At 344, an indication is communicated to the user that the DVR 104 isready to record a schedule message. This communication to the user canbe accomplished by any of the methods discussed above in relation to anemail message recording or by any other appropriate method.

The internal DVR ADPS message creation flow 300 continues from 344 to324 as discussed above for the email message recording where anindication to start recording by any one of the possible methodsdiscussed above is received and the recording process begins.Subsequently, at 328 an indication to stop the recording by any one ofthe possible methods discussed above is received and the recordingprocess stops. At 332, the internal DVR ADPS message creation flow 300ends.

If the ADPS message type selected by the user is not a schedule messageat 336, the selection is evaluated at 348 to determine whether a taskmessage was chosen. If so, other related information, such as the dateand time for the start of the task event is received at 352, by any oneof the possible methods discussed above, and this information is storedalong with the ADPS message type as will be discussed later. For taskmessages, an ending date and time may be desired. If so, the date andtime for the end of the task event is received at 356, by any one of thepossible methods discussed above, and this information is stored alongwith the ADPS message type and start date and time as will be discussedlater. As well, a priority of the task may be specified. If so, thepriority of the task is received at 360, by any one of the possiblemethods discussed above, and this information is stored along with theADPS message type, the start date and time, and the end date and time aswill be discussed later.

At 364, an indication is communicated to the user that the DVR 104 isready to record a task message. This communication to the user can beaccomplished by any of the methods discussed above in relation to emailand schedule message recording or by any other appropriate method.

The internal DVR ADPS message creation flow 300 continues from 364 to324 as discussed above for email and schedule message recording andsubsequently to 328 and to 332 where the internal DVR ADPS messagecreation flow 300 ends.

Turning now to FIG. 4, one embodiment of a data structure of an ADPSmessage 400 is shown. In this embodiment, the data associated with theaudio recording 404 is digitally encoded and stored as separate digitaldata that are concatenated to form the ADPS message header 408 that isitself concatenated with the audio recording 404.

Turning now to FIG. 5, one possible embodiment of an ADPS message header408 is shown. The message type is stored at 504. In this embodiment, themessage type represents either a standard audio recording or an ADPSmessage 116. The message type 504 allows the PC 112 to properly processthe audio portion of the message. If the audio message is a standardaudio message (or any other non-ADPS message), then the PC applicationknows not to do any processing on the file during transfer from the DVR104, but simply transfers the message to the appropriate destination aswill be discussed below in the PC application section. However, if themessage type 504 indicates that an ADPS message 116 was created, thenthe PC 112 can properly process the audio portion of the message as willalso be discussed below in the PC application section.

As well, if an ADPS message 116 was created, then other fields of theADPS message header 408 are populated with data. At a minimum, the ADPStype 508 is populated to indicate the destination PIM application forthe ADPS message 116. This ADPS type 508 can be any of the onesdiscussed above in relation to FIG. 3, or other types related to otherPIM applications in other embodiments.

As discussed above, if the ADPS message 116 is of an email type message,then no other parameters may be relevant or helpful for the PC 112 toproperly process the ADPS message 116. In this case, parameter fields512 through 520 may not be used. These fields can then either beexcluded from the header, thereby making the ADPS message header 408dynamic in length, or can be blank data fields or can be populated withother relevant parameters. However, these fields can remain withoutinhibiting the processing of the ADPS message at PC 112.

It should be noted that a dynamic or variable length for the ADPSmessage header 408 may be used as long as the PC 112 and DVR 104 have acommon understanding of what parameters exist, and their placementwithin ADPS message header 408, for each type of ADPS message 116. Withthis in mind, it should now be apparent to those skilled in the art,upon consideration of this teaching, that a header length parameter isnot necessarily relevant information, but this parameter may also beincluded in the ADPS message header 408 without inhibiting theprocessing of the ADPS message 116 on PC 112. The method by which newADPS message types are created and loaded into the DVR 104 will bediscussed below.

When the ADPS message 116 is either a schedule, task, or other messagetype as may exist in other embodiments, then the parameter fields 512through 520 are populated as appropriate for the specific ADPS type 508with the appropriate data retrieved from the user as discussed above inrelation to FIG. 3.

Other options and possibilities exist for fields in the ADPS messageheader 408. For example and without limitation, log information relatedto the discussion below can be a part of the ADPS message header 408.Flagging log information within ADPS message header 408 can be done inplace of or in conjunction with separate log creation on either the PC112 or DVR 104.

It should also be noted, as discussed above in relation to FIG. 2, thatthe voice queues, commands, or audio notes, along with many otherpossible mechanisms, could be used on the DVR 104 to initiate an ADPSmessage recording, to select the ADPS message type, and to enter anyinformation for the ADPS message. In the case of captured voice commandsor audio notes and information, this information can be stored as partof the audio recording itself thereby allowing the ADPS message header408 to contain only the message type 504.

Accordingly, an audio recording may be time stamped if the DVRincorporates an internal clock. In this case, this time-stamp parametermay be included in the ADPS message header 408 by many of the previouslydiscussed or possible alternate methods as should now be apparent tothose skilled in the art.

Turning now to FIG. 6, an exemplary ADPS download process 600 is shown.The process starts at 604. At 608, the ADPS download process 600recognizes that a DVR 104 has been connected to PC 112. A Device Pluginthat is resident on PC 112 (as discussed below) controls access to DVR104. It should be noted that the term “Device Plugin” is used hereingenerically. Any other interface that is capable of interfacing betweenthe process and the physical communication layer or communicationprotocol interface that is used to interconnect the PC 112 and the DVR104, as discussed above, can be considered consistent with thisdisclosure and the use of the term Device Plugin. At 612, priorityaccess to the Device Plugin is gained through a request/grant process.The priority access scheme is used to determine which of the possibleapplications, such as the DSA, will connect to the DVR 104. Whenpriority access to the Device Plugin is granted, ADPS download process600 determines whether there are any ADPS messages 116 on DVR 104 thatcan be processed at 616. If no messages on DVR 104 can be processed at616, ADPS download process 600 releases priority access to the DevicePlugin at 620, and the process ends at 624.

On the other hand, if there is at least one ADPS message 116 on DVR 104that can be processed at 616, the process gets (receives) an ADPSmessage 116 at 628. At 632, the ADPS type 508 is determined by readinginformation that associates the voice content with a PIM applicationfrom the ADPS message header 408. As discussed, the ADPS type 508determines the destination PIM application for the ADPS message 116.Additional parameter fields 512 through 520, when appropriate for thatmessage type, are included in the ADPS message header 408.

Depending upon the PIM application, certain enhancements to the recordedaudio message can be done by use of enhancement filtering (e.g.,transcription, enhanced audio, transcoding, or many other options asdescribed in more detail below). Based upon setup parameters in relationto the destination PIM application, ADPS download process 600 candetermine whether filter enhancements are appropriate. If adetermination that these filter enhancements are appropriate is made at636, the process transitions to 640 to process the audio portion(voice/audio content) of ADPS message 116 through the relevantenhancement filter(s) to create a post-enhancement audio portion, textportion, or both. If no enhancement processing is appropriate at 636, orafter enhancement processing at 640, the process transitions to 644.

Depending upon the destination PIM application, the ADPS message 116 maybe reformatted (or converted) to properly interface it with thedestination PIM application. If this reformatting is to be done, theADPS message 116, with post-enhancement audio portion (this could be atranscription, enhanced audio, transcoding, or many other options asdescribed in more detail below), may be reformatted for the destinationPIM, at 644. This reformatting can be a conversion between a compressedand non-compressed formats, reorganization of the message fields, or anyother type of conversion that may be possible. For example, and not byway of any limitation, a user may choose to store their email in aspace-economical format (e.g., MP3, LPAC, or other codec) fordistribution on the Internet, and may choose to store reminders in anon-space-economical format (e.g., .wav format).

At 648, the reformatted and possibly enhanced ADPS message is then sent(transferred) to a PIM through a PIM synchronization client. At 652, thereformatted and possibly enhanced ADPS message is also copied to the DSAfor archival.

At 656, both transfers (to the PIM and DSA) are confirmed and ifconfirmation is acknowledged, the ADPS message file 116 is deleted fromthe DVR 104 at 660. A log entry is created at 662 to record theprocessing. As discussed above, the log entry can be flagged in the ADPSmessage header 408 alone, or the log entry can be created on either PC112 or DVR 104. At 664, the process determines whether there are anymore ADPS messages 116 on DVR 104 that can be processed. If there aremore ADPS messages 116 on DVR 104 that can be processed, then atransition is made to 628 to process the next message. If there are nomore messages to process at 664, the process transitions to 620 toreleases priority access to the Device Plugin and then ends at 624.

Turning now to FIG. 7, ADPS download system block diagram 700 is shown.ADPS download process 600 can be implemented within ADPS download system700. ADPS system 700 augments the standard DVR-to-DSA download path 704without destroying it. Using the standard DVR-to-DSA download path 704,the message recorded on the DVR 104 can be downloaded as a file via aDVR-to-PC connection, such as USB connection 108 in this embodiment. Thefile can be transferred to the DSA 708 through a Device Plugin 712(briefly discussed above). The Device Plugin 712 manages access ofsoftware applications to the DVR 104 in order to transfer message datavia the physical communications layer (USB protocol in the presentexemplary embodiment). In order to handle recorded files, the userlaunches the DSA 708 and manages files as discussed above.

The File Processing Filter (FPF) module 716 uses ADPS path 720 tocommunicate with DVR 104 and has priority over the DVR-to-DSA downloadpath 704 in accessing the Device Plugin 712. This allows the automatedprocess to work in an uninterrupted fashion relative to DSA 708.

The FPF 716 has several responsibilities. Some of them for thisembodiment may include without limitation: to activate/deactivate theADPS feature on DVR 104, to manage file transfer from DVR 104 throughDevice Plugin 712, to process the file through the various fileenhancement filters (to be discussed below), to transfer the result ofthe file enhancement activity to the PIM Synchronization Client (to bediscussed below), to transfer the file to the DSA 708, to delete thefile from DVR 104 after download and processing is complete, to keep alog of processed files, and to grant Device Plugin 712 access to DSA 708after the automated download is complete.

Activation and deactivation of the ADPS feature on DVR 104 isaccomplished by user interaction with FPF 716. The ADPS function may beactivated on DVR 104 by a software command from PC 112. Once DVR 104 isconnected to the PC 112, the FPF 716 will first verify that the DVR isADPS activated. If it is not ADPS activated, an automatic activation maytake place. Activation will enable the enhancements discussed above inDVR 104 functionality. These enhancements can enable entry of messagecontent as well as additional information that describes the message, asdiscussed above for actions related to creating an ADPS message on theDVR. In some cases, the DVR 104 ADPS functionality can also bedeactivated. The user may specify a request to activate or deactivatethe DVR 104 ADPS functionality by interfacing with the FPF 716 through asetup screen on PC 112 or DVR 104.

Management of the file transfer from DVR 104 through Device Plugin 712can be automated in accordance with certain embodiments. The FPF 716identifies if there are files to process upon DVR 104 to PC 112connection. The FPF 716 selects those files to be processed. These filescan be transferred to PC 112 via Device Plugin 712.

Configuration of ADPS download system 700 to process the file throughthe various file enhancement filters can be accomplished through FPF 716settings. The selected enhancements to the file may be of one, several,or none of the processes available on PC 112. The selection may dependon the nature of the recording allowing, for example, email typemessages to be transcribed and schedule event type messages to beacoustically enhanced and then transcoded. The enhancing filters may beindependent software modules created by a separate manufacturer. Thesefilters may be installed, launched, and managed independently of theADPS system 700 or the FPF 716 functionality. The recorded file is fedinto these enhancing filters as an input, either sequentially or inparallel, depending upon the configuration selected for FPF 716. Theorder of processing can vary from that discussed below and such avariation is considered consistent with the processing described.

Many possibilities exist for the file enhancement filters. For example,the file enhancement filters could be a transcoder, an acousticenhancer, a transcriber, or any other file enhancement filter thatbecomes apparent to those skilled in the art in view of this disclosure.The file enhancement filters can be implemented using hardware orsoftware operating on a general purpose processor. The following orderof processing can be configured during setup.

With transcoding filter 724, the file may be transcoded. Through thetranscoding filter 724, the file is transcoded to a specified codec andthe resulting file is then output from transcoding filter 724. The filecould be transcoded to a different bit rate, changed to Variable BitRate (VBR), changed to Fixed Bit Rate (FBR), etc.

With acoustic enhancement filter 728, an acoustically enhanced file isthe output. This acoustic enhancement can include any of a variety ofacoustic enhancement measures, including but not limited to thosecommonly known to those skilled in the art. For example, limiting,clipping, compressing, expanding, notch filtering, band-pass filtering,low-pass filtering, high-pass filtering, noise reduction, equalization,noise gating, and many other audio acoustic enhancements can beperformed.

With transcribing filter 732, the output may contain the audio file aswell as a text file representing the transcribed audio content, are theoutputs. The audio file may be discarded or redirected as discussedbelow. Transcribing can be carried out using custom software, orcommercially available products such as “Dragon Naturally Speaking”available from ScanSoft, Inc.

A recorded message that was transferred is considered information. Thisinformation is ultimately intended for a destination PIM application736. This routing is done in conjunction between FPF 716 and a PIMSynchronization Client 740. Regarding the transfer of the result(s) ofthe file enhancement activity to the PIM Synchronization Client 740, theFPF 716 communicates with the PIM Synchronizing Client 740. The PIMSynchronizing client 740 is placing the audio/text body of the messagein the appropriate area of the PIM application 736. The PIMSynchronizing Client 740 may take the form of a separate softwarecomponent from the FPF 716 (but need not be a separate softwarecomponent) and may also be created by a different software manufacturer.The PIM Synchronization Client 740 may be installed and setupindependently of the ADPS system 700 or the FPF 716 functionality.However, since there are PIM Synchronization Client 740 and the FPF 716functionality dependencies, there may be advantages to using one setupprocedure for both modules.

It should be noted that PIM application 736 is represented as onecomponent. This is for ease of presentation only. There may typically bemany PIM applications on a given PC 112. PIM functions can also beincorporated into a plurality of user interfaces. Therefore, in anydiscussion about PIM application 736, the reader should keep thepossible inherent plurality of PIM applications in mind.

The user may decide to automatically download a file to the DSA 708whenever an ADPS process 600 executes on ADPS system 700. The FPF 716may download all files on DVR 104 to DSA 708. FPF 716 may also downloadonly those files that are processed for purpose of PIM management. Inthe last case, the user may want to keep a backup of the file in DSA708. As part of the FPF 716 setup process, the user may specifyautomatic file to DSA 708 download.

After downloading, processing and directing a file to the appropriatePIM application 736, the user may not desire to keep the recordedmessage on DVR 104. In that case, an automatic ‘delete file on DVR’action takes place. Note that the delete function is preceded by anacknowledgment that the message file has been stored on the PC 112 harddrive. Only when the FPF 716 receives the acknowledgment can the file bedeleted from DVR 104.

The FPF 716 can keep a log of all files processed. When a message isprocessed, it is flagged by the FPF 716. Thereby, the next time that DVR104 is connected to PC 112, the same file can be prevented from beingprocessed again. Therefore, a message recorded for purpose of an emailmessage will only appear in one email message in the email PIMapplication. Whenever, DVR 104 is connected to PC 112, FPF 716 cancompare records of files on DVR 104 to the log that has been previouslycreated. If the file has no log record on that computer, it can bedownloaded and processed as a new file. FPF 716 can also be able toidentify files modified on DVR 104, even if these files were downloadedbefore the modification. In that case, FPF 716 can either download ornot download the file depending on preference settings specified duringthe setup procedure for FPF 716. Further, as a configuration option forFPF 716, the files on DVR 104 can default to either allow them to besynchronized to multiple computers or a single computer.

One exemplary way to manage the log is by storing the log file on PC112. Another is to store the log file on DVR 104. If stored on DVR 104,the log file can record transactions to multiple computers (Personal,Business, PCx, PCy). An alternative way to track a processed file is toadd a ‘downloaded’ flag corresponding to processed files on DVR 104.Files that were downloaded using FPF 716 can be flagged as ‘downloaded,’whereas files that were not downloaded can have their ‘downloaded’ flagunaltered. When the ‘downloaded’ flag is set, there is no downloading ofthe file the next time that DVR 104 is connected to a specified PC suchas PC 112. The ‘downloaded’ flag may be one of the file's attributes andcan be changed on DVR 104 by an action taken on PC 112. FPF 716 can thenidentify which files are to be processed and which ones are not based onthat flag information. When a file that was newly created on DVR 104 isautomatically downloaded to PC 112, FPF 716 changes the flag informationof that file to ‘downloaded’. When the user selects an option not todelete a file on DVR 104 after processing and thereby allow later filemodification or copying to another PC, another option that can be set bythe user is for the ‘downloaded’ flag to be cleared when an existingfile is later modified on DVR 104, or for the ‘downloaded’ flag not tobe set when copied which allows copying to another PC. This will allowthe user to determine whether to reprocess a file if it is modified onDVR 104 or to process the file if it is to be downloaded to another PC.

The ADPS process 600 executing on ADPS System 700 only takes place oncethe DVR is connected to PC 112 via USB 108, or when removable media suchas a memory stick that contains ADPS files is inserted into PC 112. OnceFPF 716 is done with all its activities, the automated process is over.At that point, the user may launch and use DSA 708 software to managerecorded files on PC 112 or on DVR 104. In order to enable DSA 708 toaccess DVR 104 through Device Plugin 712, FPF 716 gives up its priorityfor access to Device Plugin 712. FPF 716 gives up the device accessuntil the next time that USB 108 recognizes a DVR getting connected toPC 112.

In order to enable the FPF 716 priority access to Device Plugin 712,Device Plugin 712 can be designed to allow device access by multiplemodules. Device Plugin 712 can then prioritize FPF 716 access when firstdetecting a connected DVR 104. Once FPF 716 relinquishes access toDevice Plugin 712, DSA 708 can have access to DVR 104 until the nexttime that a new DVR connection is detected. The new device connectionand detection process takes place in cases such as when a USB cable isconnected to PC 112 or when a PC 112 is starting up when a USB cable isalready connected.

Setup procedures for the above-mentioned ADPS process 600 and ADPSsystem 700 can now be discussed. Additional possibilities exist for FPF716 to activate DVR 104 and automate the ADPS process 600. A setupprocedure can be run on PC 112 that sets up the interface preferencesfor ADPS process 600 and ADPS system 700. A DVR 104 capable ofdownloading audio files to a PC 112 interacts with a DSA that allowsmanagement of these files. This functionality can be done after theinstallation and activation of the DSA 708. However, no specialactivation is required on the DVR side when the download functionalityis built into the DVR 104 firmware, though an activation mechanism maybe used to allow for the ADPS feature set to be enabled upon purchase ofthe feature set. DVR 104 may have two different patterns of behavior:Regular Behavior is capable of use for downloading an audio file fromthe DVR 104 to the DSA 708, and PIM-related Behavior is available whenan indication of an ADPS type message is made. In the PIM-relatedBehavior mode, the downloaded file is being processed and directed tothe appropriate PIM function. The PIM-related behavior capability may beactivated through an ADPS activation in order to enable a change of DVR104 behavior. In that case DVR 104 can be connected to the PC 112 andsoftware running on the PC 112 will activate this special function onDVR 104. This software activation of a device behavior is similar toclosing a power switch on an electric system. When the switch is turnedoff PIM-related functionality is not available. When the switch isturned on, the system is capable of operating in Regular as well asPIM-related Behavior mode.

In addition to activating ADPS device functionality, the setup offunctions on PC 112 to enable automatic processing of the audio contentonce it is downloaded to the PC 112 can also be done.

In order to enable automatic processing of the audio content once it isdownloaded to PC 112, several settings are possible for the setup of theFPF 716. Some of them are automatic transcription, automatictranscoding, removing or retaining the file on DVR 104 after processing,and downloading of the file to the DSA for archival.

Automatic Transcription allows an automatic transcription process suchas running a speech to text application. The user may want to use thetranscription function in conjunction with the file download (e.g.,Transcribe a file and also filter the file). The function may beassociated with all PIM functions or with a specific PIM function. So,for example, a message recorded to be an email communication may betranscribed into the email message in the PIM whereas a schedule eventmay be transferred to the PIM without automatic transcription. Inaddition, after the file is transcribed, the user may not wish to sendthe audio file itself. In that case, the user may want to edit a textmessage without dealing with the audio file embedded in that PIM'sfunction. After the editing is done, the user can send text only emailcommunication based on the transcribed audio file. The setup processenables the user to choose their preferred handling of the audio and thetranscribed files.

Automatic transcoding allows transforming a file recorded in one codecscheme to another as discussed above. Transcoding may be desired formany purposes such as further compression or use with more ubiquitousformats such as .wav or .mp3. Since native playback and recording ofaudio content may vary from one DVR model to another, transcoding mayprovide consistency with other audio content synchronized from a DVR orrecorded on the PC 112 as well as for content that may need to beuploaded from the PC to another DVR. Native transcoding may be selectedfor some PIM message types but not others in certain embodiments.

Removing or retaining a file on the DVR after download is anotherpossible option. A user may want to retain a copy of the file on the DVReven after download. In those cases, they may not want to remove themessage from the DVR after download. Removing the message after downloadcreates space on the DVR for additional audio recordings. During thesetup process the user may select their preferences for automatic ormanual removal of files from DVR 104.

Download the file to the DSA is another possible setup option. Users maywant to download a copy of a file from the DVR to the DSA. The DSA couldbe used as a backup for files that are removed from the DVR and placedin the PIM. The advantage of downloading to the DSA in addition to PIMdownload may be having a backup of audio files in the one applicationthat handles all recorded files (the DSA). In addition, the automaticdownload of all files to the DSA, may remove the action of separatelyspecifying the download within the DSA interface. The user may be givenan option to select their preferences for DSA file download.

A folder structure may assist in backup and management of files in theDSA. For example and not by way of limitation, all email ADPS messagescan be stored in a dedicated folder, while schedule ADPS messages andregular recordings can be stored in different folders.

When enabling functionality on DVR 104 and setting up the downloadsystem on the PC are completed the system is ready for recording andautomatically downloading ADPS type messages. The recorded file mayautomatically be downloaded and managed. An indication, such as an iconon the PC 112 Desktop Task Manager, may be an acknowledgment that theFPF 716 is active. In this way, a user that does not want the FPF 716 tobe resident could close the FPF 716 anytime they wish. Disabling the FPF716 immediately makes the Device Plugin 712 accessible by the DSA 708.Settings can be changed at any time by recalling the FPF 716 setupprompts on PC 112.

In view of the present teaching, one skilled in the art should now beable to recognize that many other possibilities exist for setup andconfiguration of the DVR and PC environments, and all are consideredwithin the scope of the disclosure.

Turning now to FIG. 8, a second embodiment of an ADPS system 800 isshown. DVR 104 is connected through an appropriate mechanism, such as aUSB connection 108 in this embodiment, to a PC or comparable device 112,to enable download of an ADPS message 116 from ADPS database 120, to thePC 112. As previously noted, other connection mechanisms can be used toconnect the DVR 104 to the PC 112. Connection mechanisms, such as anystandard or custom wireless protocol, removable media (e.g., FLASH,CD-R, SMARTMEDIA™ CD-RW, HDD, magnetic discs, or MiniDisc), or any othereffective communication mechanism can be used for interconnection of DVR104 to PC 112. When the DVR 104 is connected to PC 112, the ADPS message116 may be automatically downloaded to the appropriate target PIMapplication without launching the DSA. USB connection 108, or any othereffective connection, can also be used to upload settings and data 804from PC 112 to DVR 104. This upload capability allows a user to createnew and custom ADPS message formats. These new and custom messageformats may include the new ADPS type and parameter sets. This featureallows the adaptation of the ADPS system 800 to other PIM applicationsas they become available, as well as reconfiguration and augmentation ofthe existing user interface on DVR 104.

Turning now to FIG. 9, a modified internal DVR ADPS message creationflow diagram 300 is shown as internal DVR ADPS message creation flowdiagram 900. This modified version of DVR ADPS message creation flowdiagram 300 shows two of the many possible modifications a user canachieve with the user of the upload capability of ADPS system 800.

First, one can notice by inspection of the two figures that the order ofthe list of ADPS message types presented to the user can be altered. InFIG. 9, the columns of activity related to the ADPS message typeselected by the user are swapped in the list. Therefore, the scheduleADPS message evaluation 336 and the presentation of that messagecreation option to the user are before the task ADPS message evaluation348 and presentation of that message creation option to the user. Thislist ordering can represent the order of items in the ADPS message typelist as modified by the user and can alter both the internal processingof a message selection and the order of operations that are availablefor the user.

The second modification in this embodiment is that a list of addresseesfor email messages has been uploaded to DVR 104 and presented to theuser at 904. At 908, the user's selection for the addressee of the emailADPS message is received and the processing continues with the addresseeinformation becoming a new parameter in the ADPS header. As such, theuser can modify the ADPS message header and message format, theinformation available to the user during an ADPS message interactionsession, and the behavior of the DVR 104 during an ADPS messageinteraction session.

Thus, a computer readable data structure can be stored on both a DigitalVoice Recorder (DVR) and a host computer with a segment of datarepresenting a digital voice message and a header containing informationthat defines an association between the digital voice message and apersonal information manager (PIM).

It should now be apparent upon consideration of this teaching to thoseskilled in the art that many other modifications to the DVR 104environment are possible with the upload capability of ADPS system 800,such as adding a new message type, audio contact information, complexrecords, and other custom records.

Turning now to FIG. 10, the process described above for automaticdownload may be modified to create an Automatic PIM-to-DVRSynchronization (ADPS) Upload process 1000 as shown. A user may desireto take files that have been created or stored on PC 112 with them onDVR 104 when they leave home or the office. The user may configure ADPSupload process 1000 in a variety of ways (eg. to transfer all emailmessages with audio content, all events, files of a certain date ortime). The process starts at 1004. At 1008, the ADPS Upload process 1000recognizes that a DVR 104 has been connected to PC 112. A Device Pluginthat is resident on PC 112 controls access to DVR 104. At 1012, priorityaccess to the Device Plugin is gained through a request/grant process.

When priority access to the Device Plugin is granted, ADPS downloadprocess 600, described above, executes at 1014 with a pass-througheffect for blocks 612 and 620 related to Device Plugin access. When ADPSdownload process 600 completes, ADPS Upload process 1000 determines at1016 whether a message in a source PIM is already validly formatted forDVR 104. All candidate files should comply with the audio Codec enabledon the DVR 104 when eventually downloaded. Files not complying may betranscoded to the appropriate codec. Files containing text may be handedover to a text to speech filter. As such, files may be transcoded orprocessed through a text to speech filter in order to be validlyformatted for DVR 104. Based upon this teaching, it should now beapparent to those skilled in the art, that many other filters andconversions can be possible. These other possible filters arecontemplated and considered consistent with this disclosure. Therefore,if the message for DVR 104 is not validly formatted at 1016, the file isprocessed through the appropriate filter(s) at 1020, as discussed above.The file is formatted properly for DVR 104 at 1024.

Memory space on DVR 104 is another consideration. One action that can betaken in case of limited DVR space can be an automatic transcoding offiles to a lower bit-rate before upload. The transcode to a lowerbit-rate process may also take place anytime that a file is uploadedfrom the PIM to the DVR 104. In case that the message contains text aswell as audio information further processing may take place. Forexample, an email message containing audio and text information may betext-to-speech processed for the text portion, and then appended intoone message file along with the audio recording. As another example, ifspace on DVR 104 is limited, a setup selection of upload bypredetermined priority or exclusion of files larger than preset size maytake place. An interface can include an indication to the user that theupload may not take place because of DVR 104 memory limitation.

At 1028 the space on DVR 104 is validated to determine if there issufficient space for the file to be uploaded. If there is not sufficientspace determined at 1028, the process determines whether the file can betranscoded to a lower bit rate to fit the available space at 1032. Aminimal bit-rate for transcoding can be configured.

If it is determined that the file cannot be transcoded to fit theavailable space in DVR 104 at 1032, a notification is presented to theuser at 1034 indicating that the file could not be transferred and theprocess releases priority access to the Device Plugin at 1036, and theprocess ends at 1040. If it is determined that the file can betranscoded to fit the available space in DVR 104, then the processtransitions to 1020 to process the file. A formatting, as discussedabove, is done at 1024, and the space is again validated at 1028.

In either case, if there is sufficient space determined at 1028 (eitherinitially or after a transcoding), the file is copied to DVR 104 at1044. The file is also copied to the DSA at 1048. Both file transfersare confirmed and acknowledged at 1052 and the file can be deleted fromthe PIM application at 1056 depending upon configuration. A log of theprocessing can be created at 1058, also depending upon configuration.

At 1060, the process determines whether there are any more messages in aPIM application that can be processed. If there are more messages in aPIM application to process, then a transition is made to 1016 to processthe next message. If there are no more messages to process at 1060, theprocess transitions to 1036 to releases priority access to the DevicePlugin and then ends at 1040.

Thus, the DVR 104 may be used for, in addition to downloading recordedADPS messages 116 and standard audio recording, uploading PIM messages,uploading standard audio files, and uploading other audio information.

It may be desirable to distinguish between those messages uploaded fromthe PIM and other message types. In order to distinguish between thesemessages, the device may incorporate a graphical indication associatedwith files uploaded from the PIM. The special characteristics of filesuploaded from the PIM may assist in playback selection. For example,email files associated with a certain email addressee may be played backsequentially upon selecting the addressee name on the DVR. Schedulefiles may prompt the user to play back according to message timing ormay play back automatically when there is a date/time match with the DVRclock. To-do messages may be sorted and played back based on priority orcompletion date/time.

Automatic DVR to PIM download could take place in various other systems.Some commercially available PIM Synchronization Client softwareapplications are able to connect to Web-based PIM. This allows suchWeb-based PIM to be accessed from any computer upon entering a user nameand/or password. A Web-based PIM may store information on a remoteserver. Data access and management can usually be done via an Internetbrowser interface. Enabling compatibility with a Web-based PIM mayemploy a modified architecture for the FPF as well as a different typeof PIM Synchronization Client to accommodate for data storage on aremote server.

The FPF can accommodate the possibility that a connection with the webbased PIM is not established immediately. Most tasks of the FPF canstill take place. However, since an immediate download of content andacknowledgment from the PIM Synchronization Client may not be available,a delayed activity may take place. Action such as removing a messagefrom the DVR or flagging a file already downloaded to the PC may bepostponed. A message that was not downloaded because of inability toaccess a remote server may be stored locally on a PC for a laterdownload. Once the download takes place an acknowledgement can be sentby the PIM Synchronization Client to the FPF.

Some components of the PIM Synchronization Client may reside on theremote server. These components place the message in the appropriatestorage place in the server. However, the components that directlycommunicate with the FPF have to reside on the PC where the FPF resides.

Further, in some cases it may be desired to download content to the PIMappropriate function without connecting to a PC at all. In those casesthe PIM itself may still be accessible via a PC and may be interfacedeither via a PIM software client or a Web-based interface. Similar to aWeb-based PIM case, the design of the system can be adapted or modifiedin order to accommodate for delays and issues related to communicationfrom the DVR to the PIM.

Turning now to FIG. 11, an exemplary block diagram of a DVR 1100 capableof implementing the DVR-side ADPS methods discussed above is shown. DVR1100 has a central processor unit (CPU) 1104 with an associated bus 1108used to connect the central processor unit 1104 to Random Access Memory1112 and/or Non-Volatile Memory 1116 in a known manner. An outputmechanism at 1120 may be provided in order to connect to a computer ofan APDS system. It should be noted that, in addition, DVR 1100 mayincorporate a mechanism to directly communicate with a computer networksuch as the Internet, or a local or wide area network, without the needto connect directly to a computer. The communication can take placeusing a wired or wireless method. In these cases the DVR can downloadmessages by use of a built in or external modem. External connection maybe implemented by any connection device such as dedicated externalmodem, PDA with a built in modem, and a Cellular Phone with voice anddata capabilities, along with many other methods. In all these cases,the system can maintain its functionality and may incorporate some ofthe remote functions such as those described above related to aWeb-based PIM. In this type of implementation the FPF can reside on aremote computer or server. The DVR can be modified to enablecommunication with the remote FPF. Similarly, input devices such as amicrophone and input select devices, or USB input 1124 may be providedfor the input of information by the DVR 1100 user or from a personalcomputer. Further, a voice recognition capability can be added, asdiscussed above, in either a hardware or software embodiment, to enablevoice command interpretation and recognition as a part of the input 1124for use in a user interface of DVR 1100.

Turning now to FIG. 12, an exemplary block diagram of a computer system1200 capable of implementing the PC-side ADPS methods discussed above isshown. Computer system 1200 has a central processor unit (CPU) 1210 withan associated bus 1215 used to connect the central processor unit 1210to Random Access Memory 1220 and/or Non-Volatile Memory 1230 in a knownmanner. Computer system 1200 can perform such functions as controllingthe ADPS processes described above, PIM application(s), file transfer,file enhancement filtering, formatting, logging, and other functionsdiscussed above and contemplated by the above discussion. An outputmechanism at 1240 may be provided in order to display and/or printoutput for the computer user and to interface to the DVR for ADPSsynchronization by any of the methods discussed above. Similarly, inputdevices such as keyboard and mouse 1250 may be provided for the input ofinformation by the computer user. Computer 1200 also may have discstorage 1260 for storing large amounts of information including, but notlimited to, program files and data files. Computer system 1200 may becoupled to a local area network (LAN) and/or wide area network (WAN)and/or the Internet using a network connection 1270 such as an Ethernetadapter coupling computer system 1200, possibly through a firewall.

Those skilled in the art will recognize that certain of the exemplaryembodiments described herein are based upon use of a programmedprocessor. However, the invention should not be so limited, sincecertain embodiments could be implemented using hardware componentequivalents such as special purpose hardware and/or dedicated processorswhich are equivalents to the invention as described and claimed.Similarly, general purpose computers, microprocessor based computers,micro-controllers, optical computers, analog computers, dedicatedprocessors and/or dedicated hard wired logic may be used to constructalternative equivalent embodiments of the present invention.

Those skilled in the art will appreciate that the program actions andassociated data used to implement the embodiments described above can beimplemented using disc storage as well as other forms of storage such asfor example Read Only Memory (ROM) devices, Random Access Memory (RAM)devices; optical storage elements, magnetic storage elements,magneto-optical storage elements, flash memory, core memory and/or otherequivalent storage technologies without departing from the presentinvention. Such alternative storage devices should be consideredequivalents.

Certain embodiments as described herein, can be implemented using aprogrammed processor executing programming instructions that are broadlydescribed above in flow chart form that can be stored with theassociated data on any suitable electronic computer readable storagemedium. However, those skilled in the art will appreciate that theprocesses described above can be implemented in any number of variationsand in many suitable programming languages without departing from thepresent invention. For example, the order of certain operations carriedout can often be varied, additional operations can be added oroperations can be deleted without departing from the invention. Errortrapping can be added and/or enhanced and variations can be made in userinterface and information presentation without departing from thepresent invention. Such variations are contemplated and consideredequivalent.

While the invention has been described in conjunction with specificembodiments, it is evident that many alternatives, modifications,permutations and variations will become apparent to those skilled in theart in light of the foregoing description. Accordingly, it is intendedthat the present invention embrace all such alternatives, modificationsand variations as fall within the scope of the appended claims.

1. A computer readable medium storing instructions which, when executedon a programmed processor, carry out a process of: receiving at leastone voice file containing audio content and related information from adigital voice recorder (DVR); reading information in the voice file thatassociates audio content within the voice file with at least onepersonal information manager (PIM) application executed by theprogrammed processor, where the at least one PIM application comprises auser productivity enhancing application; and processing the voice fileby transferring the voice file to the at least one PIM application. 2.The computer readable medium of claim 1, further storing instructionswhich, when executed on a programmed processor, carry out a process of:processing the audio content through at least one enhancement filter tocreate enhanced audio content prior to transferring the voice file to aPIM application.
 3. The computer readable medium of claim 2, furtherstoring instructions which, when executed on a programmed processor,carry out a process of: reformatting the voice file along with theenhanced audio content to interface the voice file with a PIMapplication thereby creating a reformatted voice file.
 4. The computerreadable medium of claim 3, further storing instructions which, whenexecuted on a programmed processor, carry out a process of transferringthe reformatted voice file to a PIM application.
 5. The computerreadable medium of claim 4, further storing instructions which, whenexecuted on a programmed processor, carry out a process of copying thereformatted voice file to a DVR Dedicated Software Application (DSA). 6.The computer readable medium of claim 5, further storing instructionswhich, when executed on a programmed processor, carry out a process ofsending a command to the DVR instructing the DVR to delete the voicefile from the DVR.
 7. The computer readable medium of claim 6, furthercreating a log entry to record transferring the reformatted voice fileto the PIM application and copying the reformatted voice file to the DVRDedicated Software Application (DSA).
 8. An apparatus for AutomatedDigital voice recorder to Personal information manager Synchronization(ADPS), comprising: an interface that receives at least one voice filecontaining audio content and related information from a digital voicerecorder (DVR); a memory; and a programmed processor that readsinformation in the voice file that associates audio content within thevoice file with a personal information manager (PIM) applicationexecuted by the programmed processor, that processes the voice file bytransferring the voice file to at least one PIM application, where thePIM application comprises a user productivity enhancing application. 9.The apparatus of claim 8, wherein the programmed processor furtherstores the voice file in the memory.
 10. The apparatus of claim 8,wherein the programmed processor processes the audio content using atleast one enhancement filter to create enhanced audio content prior totransferring the voice file to a PIM application.
 11. The apparatus ofclaim 10, wherein the enhancement filter comprises at least one of atranscription filter, an enhanced audio filter, and a transcodingfilter.
 12. The apparatus of claim 8, wherein the programmed processor:reformats the voice file to interface the voice file with a PIMapplication to create a reformatted voice file; and transfers thereformatted voice file to the PIM application.
 13. The apparatus ofclaim 12, wherein the programmed processor copies the reformatted voicefile to a DVR Dedicated Software Application (DSA).
 14. The apparatus ofclaim 13, wherein the programmed processor sends a command to the DVRinstructing the DVR to delete the voice file from the DVR.
 15. Theapparatus of claim 14, wherein the programmed processor creates a logentry to record transferring the reformatted voice file to the PIMapplication and copying the reformatted voice file to the DVR DedicatedSoftware Application (DSA).
 16. The apparatus of claim 8, wherein theprogrammed processor copies the voice file to a DVR Dedicated SoftwareApplication (DSA).
 17. The apparatus of claim 8, wherein the programmedprocessor sends a command to the DVR instructing the DVR to delete thevoice file from the DVR.
 18. The apparatus of claim 8, wherein theprogrammed processor creates a log entry to record transferring thevoice file to the at least one PIM application.
 19. The apparatus ofclaim 18, wherein the programmed processor: stores the voice file in thememory; processes the audio content through at least one enhancementfilter to create enhanced audio content; reformats the voice file alongwith the enhanced audio content to interface the voice file with a PIMapplication to create a reformatted voice file; transfers thereformatted voice file to a PIM application; copies the reformattedvoice file to a DVR Dedicated Software Application (DSA); sends acommand to the DVR instructing the DVR to delete the voice file from theDVR; and creates a log entry to record transferring the reformattedvoice file to the PIM application and copying the reformatted voice fileto the DVR Dedicated Software Application (DSA).
 20. The apparatusaccording to claim 8, wherein the interface comprises one of a universalserial bus (USB) interface, a serial interface, a parallel interface, anIEEE-1394 compliant interface, an infrared interface, an Ethernetinterface, and a wireless interface.
 21. An apparatus for AutomatedDigital voice recorder to Personal information manager Synchronization(ADPS), comprising: an interface that enables file transfer to a DigitalVoice Recorder (DVR); and a programmed processor that transfers at leastone voice file containing audio content and related information from aPersonal Information Manager (PIM) application across the interface tothe DVR, where the PIM application comprises a user productivityenhancing application.
 22. A data structure stored on a computerreadable storage medium, comprising: a segment of data representing adigital voice message; and a header containing information that definesan association between the digital voice message and a personalinformation manager (PIM) application, where the PIM applicationcomprises a user productivity enhancing application.
 23. The computerreadable data structure stored on the computer readable storage mediumaccording to claim 22, wherein the header contains a message type fieldthat determines if the digital voice message is an ADPS (AutomatedDigital voice recorder to Personal information manager Synchronization)message or a non-ADPS message, wherein ADPS messages have an associationwith a PIM program.
 24. The computer readable data structure stored onthe computer readable storage medium according to claim 23, wherein, ifthe digital voice message is designated as an ADPS message, the headercontains an ADPS type field that defines a specific PIM programassociated with the digital voice message.
 25. The computer readabledata structure stored on the computer readable storage medium accordingto claim 24, wherein the specific PIM program comprises at least one ofan email program, a schedule program, a task manager program, timemanagement, responsibility tracking, address management, to-do list, anda calendar program.
 26. The computer readable data structure stored onthe computer readable storage medium according to claim 24, furthercomprising at least one parameter field containing parameters associatedwith the specific PIM program.
 27. The computer readable data structurestored on the computer readable storage medium according to claim 22,wherein the header contains a log field that identifies logged eventsassociated with the digital voice message.